Add triggering_user_name to DagRunProtocol interface by dheerajturaga · Pull Request #56193 · apache/airflow

dheerajturaga · 2025-09-29T04:46:05Z

Enable tasks running in isolated environments to access the username
that triggered a DAG run without requiring direct database access.

Changes:

Add triggering_user_name field to DagRunProtocol interface
Update task-sdk DagRun data model to include triggering_user_name
Update execution API DagRun model to include triggering_user_name
Ensure field flows from database through API to task context

This allows developers to identify DAG run triggers from within task
code using the existing DagRunProtocol interface.

def find_owner(dag_run: DagRunProtocol) -> str:
    """
    Extract the owner information from the DAG run.

    Args:
        dag_run: The DAG run protocol object containing run information

    Returns:
        str: Information about who triggered the DAG run
    """
    triggering_user = dag_run.triggering_user_name

    if triggering_user:
        return f"DAG was triggered by user: {triggering_user}"
    else:
        return "DAG was triggered automatically (no user specified)"

Enable tasks running in isolated environments to access the username that triggered a DAG run without requiring direct database access. Changes: - Add triggering_user_name field to DagRunProtocol interface - Update task-sdk DagRun data model to include triggering_user_name - Update execution API DagRun model to include triggering_user_name - Ensure field flows from database through API to task context This allows developers to identify DAG run triggers from within task code using the existing DagRunProtocol interface.

dheerajturaga · 2025-09-29T04:51:53Z

cc: @jscheffl

jscheffl

Looks reasonable for me.

dheerajturaga · 2025-10-09T18:43:40Z

Cc: @kaxil I would like this in 3.1.1

jscheffl · 2025-10-09T19:55:48Z

Adding backport label but leave the decision to @kaxil if OK to backport as not a classic bug fix but a minor feature

kaxil · 2025-10-10T05:34:50Z

Cc: @kaxil I would like this in 3.1.1

https://github.com/apache/airflow/blob/main/contributing-docs/19_execution_api_versioning.rst -- We would need to add a Cadwyn migration.

Check examples in https://github.com/apache/airflow/tree/main/airflow-core/src/airflow/api_fastapi/execution_api/versions

Add backward compatibility migration for the new triggering_user_name field added to the DagRun model in the Execution API. This ensures older API clients continue to work seamlessly with newer API servers.

dheerajturaga · 2025-10-11T14:44:55Z

cc: @kaxil this looks good?

airflow-core/tests/unit/api_fastapi/execution_api/versions/head/test_task_instances.py

kaxil

1 test suggestion otherwise lgtm

) * Add triggering_user_name to DagRunProtocol interface Enable tasks running in isolated environments to access the username that triggered a DAG run without requiring direct database access. Changes: - Add triggering_user_name field to DagRunProtocol interface - Update task-sdk DagRun data model to include triggering_user_name - Update execution API DagRun model to include triggering_user_name - Ensure field flows from database through API to task context This allows developers to identify DAG run triggers from within task code using the existing DagRunProtocol interface. * Fix tests! * Add Cadwyn migration for triggering_user_name field in DagRunProtocol Add backward compatibility migration for the new triggering_user_name field added to the DagRun model in the Execution API. This ensures older API clients continue to work seamlessly with newer API servers. * Add tests for older versions where triggering user is missing * Remove triggering user from v2025-04-28 * Add a test with triggering_user_name set (cherry picked from commit 3120146) Co-authored-by: Dheeraj Turaga <dheerajturaga@gmail.com>

github-actions · 2025-10-13T23:45:54Z

Backport successfully created: v3-1-test

Status	Branch	Result
✅	v3-1-test

…che#56193) * Add triggering_user_name to DagRunProtocol interface Enable tasks running in isolated environments to access the username that triggered a DAG run without requiring direct database access. Changes: - Add triggering_user_name field to DagRunProtocol interface - Update task-sdk DagRun data model to include triggering_user_name - Update execution API DagRun model to include triggering_user_name - Ensure field flows from database through API to task context This allows developers to identify DAG run triggers from within task code using the existing DagRunProtocol interface. * Fix tests! * Add Cadwyn migration for triggering_user_name field in DagRunProtocol Add backward compatibility migration for the new triggering_user_name field added to the DagRun model in the Execution API. This ensures older API clients continue to work seamlessly with newer API servers. * Add tests for older versions where triggering user is missing * Remove triggering user from v2025-04-28 * Add a test with triggering_user_name set (cherry picked from commit 3120146) Co-authored-by: Dheeraj Turaga <dheerajturaga@gmail.com>

* Add triggering_user_name to DagRunProtocol interface Enable tasks running in isolated environments to access the username that triggered a DAG run without requiring direct database access. Changes: - Add triggering_user_name field to DagRunProtocol interface - Update task-sdk DagRun data model to include triggering_user_name - Update execution API DagRun model to include triggering_user_name - Ensure field flows from database through API to task context This allows developers to identify DAG run triggers from within task code using the existing DagRunProtocol interface. * Fix tests! * Add Cadwyn migration for triggering_user_name field in DagRunProtocol Add backward compatibility migration for the new triggering_user_name field added to the DagRun model in the Execution API. This ensures older API clients continue to work seamlessly with newer API servers. * Add tests for older versions where triggering user is missing * Remove triggering user from v2025-04-28 * Add a test with triggering_user_name set

dheerajturaga · 2025-10-22T21:35:08Z

@kaxil , the milestone needs to be 3.1.1? This seems to be missing from 3.1.1rc1

* Add triggering_user_name to DagRunProtocol interface Enable tasks running in isolated environments to access the username that triggered a DAG run without requiring direct database access. Changes: - Add triggering_user_name field to DagRunProtocol interface - Update task-sdk DagRun data model to include triggering_user_name - Update execution API DagRun model to include triggering_user_name - Ensure field flows from database through API to task context This allows developers to identify DAG run triggers from within task code using the existing DagRunProtocol interface. * Fix tests! * Add Cadwyn migration for triggering_user_name field in DagRunProtocol Add backward compatibility migration for the new triggering_user_name field added to the DagRun model in the Execution API. This ensures older API clients continue to work seamlessly with newer API servers. * Add tests for older versions where triggering user is missing * Remove triggering user from v2025-04-28 * Add a test with triggering_user_name set

kaxil · 2025-10-22T22:01:38Z

Didn't include it in 3.1.1 since it isn't a bugfix

dheerajturaga · 2025-10-22T22:04:41Z

Didn't include it in 3.1.1 since it isn't a bugfix

Can we include it? I remember you mentioned it shouldn't be a problem. especially now since we have cadwyn migration added aswell. Its a significant item for our workflows given there's no way in airflow3 to identify dagrun owner in the task

kaxil · 2025-10-22T22:07:27Z

Didn't include it in 3.1.1 since it isn't a bugfix

Can we include it? I remember you mentioned it shouldn't be a problem. especially now since we have cadwyn migration added aswell. Its a significant item for our workflows given there's no way in airflow3 to identify dagrun owner in the task

I did but unfortunately couldn't justify it as a bugfix when cherry-picking so had changed the milestone attached to it. I really do not want to risk 3.1.1 since there were a couple of high-priority bugfixes in it.

kaxil · 2025-10-22T22:24:40Z

Ok looking back and tracking it -- Fix tasks unable to access triggering_user_name` is a better PR title and is a bugfix since technically it indeed was one of the use-case for #51738 .

We will have it in 3.1.2

* Add triggering_user_name to DagRunProtocol interface Enable tasks running in isolated environments to access the username that triggered a DAG run without requiring direct database access. Changes: - Add triggering_user_name field to DagRunProtocol interface - Update task-sdk DagRun data model to include triggering_user_name - Update execution API DagRun model to include triggering_user_name - Ensure field flows from database through API to task context This allows developers to identify DAG run triggers from within task code using the existing DagRunProtocol interface. * Fix tests! * Add Cadwyn migration for triggering_user_name field in DagRunProtocol Add backward compatibility migration for the new triggering_user_name field added to the DagRun model in the Execution API. This ensures older API clients continue to work seamlessly with newer API servers. * Add tests for older versions where triggering user is missing * Remove triggering user from v2025-04-28 * Add a test with triggering_user_name set (cherry picked from commit 3120146)

kaxil · 2025-10-31T14:47:40Z

Has been cherry-picked as faeb1bf

dheerajturaga requested review from amoghrajesh, ashb and kaxil as code owners September 29, 2025 04:46

boring-cyborg bot added area:API Airflow's REST/HTTP API area:task-sdk labels Sep 29, 2025

Fix tests!

d5c7baf

jscheffl approved these changes Sep 29, 2025

View reviewed changes

jscheffl added the backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch label Oct 9, 2025

dheerajturaga added 3 commits October 11, 2025 00:25

Add Cadwyn migration for triggering_user_name field in DagRunProtocol

c282763

Add backward compatibility migration for the new triggering_user_name field added to the DagRun model in the Execution API. This ensures older API clients continue to work seamlessly with newer API servers.

Add tests for older versions where triggering user is missing

6cc81e4

Remove triggering user from v2025-04-28

cbc4ced

kaxil reviewed Oct 13, 2025

View reviewed changes

airflow-core/tests/unit/api_fastapi/execution_api/versions/head/test_task_instances.py Show resolved Hide resolved

kaxil approved these changes Oct 13, 2025

View reviewed changes

Add a test with triggering_user_name set

09f7ddf

kaxil approved these changes Oct 13, 2025

View reviewed changes

kaxil merged commit 3120146 into apache:main Oct 13, 2025
111 checks passed

dheerajturaga deleted the feature/trigger-user-in-dagrunprotocol branch October 13, 2025 23:57

kaxil added this to the Airflow 3.2.0 milestone Oct 16, 2025

kaxil modified the milestones: Airflow 3.2.0, Airflow 3.1.2 Oct 22, 2025

This was referenced Oct 31, 2025

Sync v3-1-stable with 3.1.2rc1 changes #57640

Merged

Status of testing of Apache Airflow 3.1.2rc2 & Task SDK 1.1.2rc2 #57648

Closed

Conversation

dheerajturaga commented Sep 29, 2025

Uh oh!

dheerajturaga commented Sep 29, 2025

Uh oh!

jscheffl left a comment

Choose a reason for hiding this comment

Uh oh!

dheerajturaga commented Oct 9, 2025

Uh oh!

jscheffl commented Oct 9, 2025

Uh oh!

kaxil commented Oct 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dheerajturaga commented Oct 11, 2025

Uh oh!

Uh oh!

kaxil left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions bot commented Oct 13, 2025

Backport successfully created: v3-1-test

Uh oh!

dheerajturaga commented Oct 22, 2025

Uh oh!

kaxil commented Oct 22, 2025

Uh oh!

dheerajturaga commented Oct 22, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kaxil commented Oct 22, 2025

Uh oh!

kaxil commented Oct 22, 2025

Uh oh!

kaxil commented Oct 31, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

kaxil commented Oct 10, 2025 •

edited

Loading

dheerajturaga commented Oct 22, 2025 •

edited

Loading